System and Method for Allocating An Anchoring Point for a Mobile Terminal

ABSTRACT

A first network configured to connect a terminal to a home network during a time that the terminal is roaming within the first network. The first network includes a plurality of attachment points, wherein a first attachment point is configured to receive an attach request from the terminal, and wherein the attach request includes a request from the terminal for an IP address from an anchoring point within the home network. The first network further includes an Authentication/Authorization/Accounting server proxy configured to determine whether the terminal is authorized to attach to the first attachment point, wherein in response to the terminal being authorized to attach to the first attachment point, i) a first tunnel is created between the first attachment point and a second attachment point, and ii) a second tunnel is created between the second attachment point and the anchoring point within the home network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This present disclosure is a continuation of U.S. application Ser. No.12/167,624, filed on Jul. 3, 2008, which claims priority under 35 U.S.C.§119(e) to U.S. Provisional Application No. 60/950,440, filed on Jul.18, 2007 and U.S. Provisional Application No. 60/965,355, filed on Aug.20, 2007.

FIELD

The present disclosure relates to network systems and more particularlyto mobile terminal communications within network systems.

BACKGROUND

The background description provided herein is for the purpose ofgenerally presenting the context of the disclosure. Work of thepresently named inventors, to the extent the work is described in thisbackground section, as well as aspects of the description that may nototherwise qualify as prior art at the time of filing, are neitherexpressly nor impliedly admitted as prior art against the presentdisclosure.

Referring now to FIG. 1, a functional block diagram of a wirelessnetwork system is presented. A home network 102 receives packets fromand sends packets to a packet data network (PDN) 104 that may include adistributed communications system, such as the Internet. A wirelessterminal 106 wirelessly connects to the home network 102. For example,the wireless terminal 106 may be a mobile phone, and the home network102 may be a cellular network of a mobile phone operator. The wirelessterminal 106 is configured to work with the home network 102 and may beunable connect to networks of other carriers. In variousimplementations, the wireless terminal 106 may be able to view contentfrom the PDN 104 via the home network 102. The home network 102 may alsointerconnect with various other networks that correspond to respectiveservice providers, including service providers in other countries.

Referring now to FIG. 2, a functional block diagram of a wirelessnetwork system offering mobility is presented. The home network 102 isconnected to one or more visited networks 110. For example, FIG. 2depicts three visited networks 110-1, 110-2 and 110-3. In variousimplementations, the visited networks 110 may be the various othernetworks discussed above.

A mobile wireless terminal 120 includes mobility features and may thusimplement host-based mobility. The mobility features allow the mobilewireless terminal 120 to communicate with the visited networks 110. Forexample, in FIG. 2, the mobile wireless terminal 120 has established awireless connection to the visited network 110-1. The mobile wirelessterminal 120 includes code and data used to communicate with the homenetwork 102 via the visited network 110-1. For example, the mobilewireless terminal 120 may implement a Common Management InformationProtocol (CMIP). In this way, the mobile wireless terminal 120 caninterface with the home network 102 even when connected to one of thevisited networks 110.

Referring now to FIG. 3, a functional block diagram depicts a wirelessnetwork system that provides proxy mobility to the wireless terminal106. A home network 150 communicates with visited networks 160-1, 160-2,and 160-3. The visited networks 160 provide transparent mobility towireless terminals, such as the wireless terminal 106, that have notbeen updated to include mobility functionality.

When the wireless terminal 106 attempts to establish a link with thevisited network 160-1, the visited network 160-1 determines the networkto which the wireless terminal 106 belongs. In this case, the visitednetwork 160-1 determines that the home network 150 is the appropriatenetwork. The visited network 160-1 then forwards packets from thewireless terminal 106 to the home network 150 and passes packets fromthe home network 150 to the wireless terminal 106. The wireless terminal106 may therefore be oblivious to the fact that it is connected to thevisited network 160-1 instead of to the home network 150.

Referring now to FIG. 4, a more detailed functional block diagram of animplementation of proxy mobility is presented. Proxy mobility may alsobe referred to as network-based mobility because the network providesmobility to a terminal that may not have built-in mobility. In anInternet Protocol (IP) network, proxy mobility may be referred to asproxy mobile IP (PMIP). The home network 150 includes a home agent (HA)202. The HA 202 establishes the logical location of the wirelessterminal 106. Packets destined for the wireless terminal 106 are firstsent to the HA 202, while packets from the wireless terminal 106 willappear to originate from the HA 202.

The wireless terminal 106 may establish a connection to an attachmentpoint 206-1 within the visited network 160-1. In variousimplementations, additional attachment points, such as attachment points206-2 and 206-3, may be present. The attachment points 206 maycommunicate with other networks, including the home network 150, via agateway 210.

Referring now to FIG. 5, a timeline of steps performed when the wirelessterminal 106 connects to the visited network 160-1 is presented. First,the wireless terminal 106 performs access and authentication with theattachment point 206-1. This may include communicating with an Access,Authentication, and Accounting (AAA) server. Upon authentication, thewireless terminal 106 attempts to attach to the attachment point 206-1.

The AAA server may use an identifier of the wireless terminal 106, suchas a network address identifier, that uniquely identifies the wirelessterminal 106. The attachment request requests an IP address from theattachment point 206-1. The attachment point 206-1 determines theappropriate HA for the wireless terminal 106. This information may besupplied by the wireless terminal 106 and/or may be supplied by thesource of the authentication information.

The attachment point 206-1 then sends a binding update message to the HA202. The HA 202 allocates an IP address, IP₁, to the wireless terminal106. The address IP₁ is used for communications with the wirelessterminal 106. When the wireless terminal 106 sends a packet, that packetwill appear to originate from the HA 202 with a source address of IP₁.In addition, packets destined for the wireless terminal 106 are sent tothe HA 202 with a destination of IP₁. In other words, IP₁ is used forpacket exchanges while an address of the HA 202 is not used.

The HA 202 sends a binding acknowledgement message including IP₁ to theattachment point 206-1. A tunnel is then set up between the attachmentpoint 206-1 and the HA 202 for transmission of packets to and from thewireless terminal 106. The attachment point 206-1 then assigns IP₁ tothe wireless terminal 106. In this process, the wireless terminal 106has requested an IP address from the attachment point 206-1 and hasreceived one. The wireless terminal 106 may not be aware that it isconnected to the visited network 160 or the home network 150.

Referring now to FIGS. 6 and 7, a packet being sent by the wirelessterminal 106 and a packet being sent to the wireless terminal 106,respectively, are graphically depicted. Referring now to FIG. 6, apacket 242 is transmitted to the wireless terminal 106. The source ofthe packet 242 is IP₁, the IP address assigned to the wireless terminal106. The destination of the packet 242 is the IP address, denotedIP_(dest), to which the wireless terminal 106 is sending the packet 242.IP_(dest) corresponds to a location in the PDN 104. The packet 242 mayalso include a payload.

The packet 242 is received by the attachment point 206-1. The attachmentpoint 206-1 tunnels the packet 242 to the HA 202. The packet 242 istunneled by encapsulating it within an encapsulating packet 244. Theheader and payload of the packet 242 is placed in the payload of theencapsulating packet 244. The encapsulating packet 242 has a sourceaddress of the attachment point 206-1, IP_(AP), and a destinationaddress of the HA 202, IP_(HA).

When the HA 202 receives the encapsulating packet 244, the HA 202extracts the original packet 242 from the payload of the encapsulatingpacket 244. The packet 242 is then routed to the destination indicatedby IP_(dest). For example, this may be an address on the PDN 104.

Referring now to FIG. 7, a packet 252 is received by the HA 202 for thewireless terminal 106. The packet 252 has a source address of the senderof the packet 252, designated IP_(src). The destination address of thepacket 252 is the address assigned to the wireless terminal 106, IP₁.The HA 202 recognizes the destination address of IP₁ and tunnels thepacket 252 to the attachment point 206-1.

The packet 252 may be tunneled by encapsulating it within the payload ofan encapsulating packet 254. The source address of the encapsulatingpacket 254 is the address of the HA 202, IP_(HA). The destination of theencapsulating packet 254 is the address of the attachment point 206-1,IP_(AP). The attachment point 206-1 extracts the packet 252 from thepayload of the encapsulating packet 254 and forwards the packet 252 tothe wireless terminal 106.

SUMMARY

A mobile terminal includes an Internet Protocol (IP) address module thatrequests and receives a first IP address from a home anchoring pointwithin a home network. The first IP address is an address of the homeanchoring point. The system also includes a packet module that exchangespackets with the home anchoring point via a first attachment point. Thepackets include the first IP address.

In other features, the IP address module requests and receives the firstIP address when the mobile terminal is establishing connectivity withthe home network. The system also includes a mobility management modulethat selects one of host based IP mobility management and network basedIP mobility management for the mobile terminal. The IP mobilitymanagement includes at least one of a Common Management InformationProtocol (CMIP), a proxy mobile IP (PMIP) and General Packet RadioService Tunneling Protocol (GTP).

In other features, the packet module exchanges packets with the homeanchoring point via a second attachment point when the mobile terminalis roaming within a range of the second attachment point. The mobilitymanagement module selects the host based IP mobility for communicatingwith the home anchoring point via the second attachment point. The firstIP address corresponds to a public IP address for the home anchoringpoint. One of the packets further includes a second IP address thatincludes an IP source address for payload data of the one of thepackets.

In other features, the IP source address indicates a location within apacket data network from which the payload data originated. The systemalso includes an access module that requests connection to the firstattachment point. The packet module encapsulates outgoing ones of thepackets with the first IP address, payload data, and a second IP addressthat identifies a destination within a packet data network for thepayload data. The packet module encapsulates outgoing ones of thepackets with a source IP address for the mobile terminal. The mobileterminal selects one of a plurality of types of mobility management.

In other features, the system includes the home anchoring point. Thehome anchoring point selectively provides the first IP address based onthe selected one of the plurality of types of mobility management. Thesystem also includes a visited network. The mobile terminal requests theconnection to the first attachment point when roaming in the visitednetwork. The mobile terminal requests the connection to the firstattachment point when roaming in one of the home network.

In other features, a home anchoring point is located within a homenetwork. The home anchoring point includes a public address module thatselectively provides a public address for the home anchoring point inresponse to selection of the home anchoring point by a device of thehome network. The selection is based on a private address for the homeanchoring point. The public address is requested by and is directlyaddressable by a mobile terminal. The system also includes a packetmodule that exchanges packets with the mobile terminal. The packetsinclude the public address. At least one of the public and privateaddresses includes an Internet protocol (IP) address.

In other features, the system includes a mobility management module thatdetermines whether the home anchoring point supports a request formobility from the mobile terminal. The request for mobility includes arequest to use one of a Common Management Information Protocol (CMIP), aproxy mobile IP (PMIP) and General Packet Radio Service TunnelingProtocol (GTP). One of the packets further includes a second addressthat includes an IP source address for payload data of the one of thepackets. The IP source address indicates a location within a packet datanetwork from which the payload data originated.

In other features, the packet module encapsulates outgoing ones of thepackets with the first address, payload data, and a second address thatidentifies a source within a packet data network for the payload data.The packet module encapsulates outgoing ones of the packets with a thirdaddress that corresponds to the mobile terminal.

In other features, a method for operating a mobile terminal includesrequesting a first Internet protocol (IP) address from a home anchoringpoint within a home network. The method also includes receiving thefirst IP address from the home anchoring point. The first IP address isan address of the home anchoring point. The method also includesexchanging packets with the home anchoring point via a first attachmentpoint. The packets include the first IP address.

In other features, the method includes requesting and receiving thefirst IP address when the mobile terminal is establishing connectivitywith the home network. The method also includes selecting one of hostbased IP mobility management and network based IP mobility managementfor the mobile terminal. The IP mobility management includes at leastone of a Common Management Information Protocol (CMIP), a proxy mobileIP (PMIP) and General Packet Radio Service Tunneling Protocol (GTP). Themethod also includes exchanging packets with the home anchoring pointvia a second attachment point when the mobile terminal is roaming withina range of the second attachment point.

In other features, the method includes selecting the host based IPmobility for communicating with the home anchoring point via the secondattachment point. The first IP address corresponds to a public IPaddress for the home anchoring point. One of the packets furtherincludes a second IP address that includes an IP source address forpayload data of the one of the packets. The IP source address indicatesa location within a packet data network from which the payload dataoriginated.

In other features, the method includes requesting connection to thefirst attachment point. The method also includes encapsulating outgoingones of the packets with the first IP address, payload data, and asecond IP address that identifies a destination within a packet datanetwork for the payload data. The method also includes encapsulatingoutgoing ones of the packets with a source IP address for the mobileterminal. The method also includes selecting one of a plurality of typesof mobility management. The method also includes selectively providingthe first IP address based on the selected one of the plurality of typesof mobility management.

In other features, a method for operating a home anchoring point withina home network is disclosed. The method includes selectively providing apublic address for the home anchoring point in response to selection ofthe home anchoring point by a device of the home network. The selectionis based on a private address for the home anchoring point. The publicaddress is requested by and is directly addressable by a mobileterminal. The method also includes exchanging packets with the mobileterminal. The packets include the public address. At least one of thepublic and private addresses includes an Internet protocol (IP) address.

In other features, the method also includes determining whether the homeanchoring point supports a request for mobility from the mobileterminal. The request for mobility includes a request to use one of aCommon Management Information Protocol (CMIP), a proxy mobile IP (PMIP)and General Packet Radio Service Tunneling Protocol (GTP). One of thepackets further includes a second address that includes an IP sourceaddress for payload data of the one of the packets.

In other features, the IP source address indicates a location within apacket data network from which the payload data originated. The methodalso includes encapsulating outgoing ones of the packets with the firstaddress, payload data, and a second address that identifies a sourcewithin a packet data network for the payload data. The method alsoincludes encapsulating outgoing ones of the packets with a third addressthat corresponds to the mobile terminal.

In other features, a mobile terminal includes Internet Protocol (IP)address means for requesting and receiving a first IP address from homeanchoring point means for anchoring within a home network. The first IPaddress is an address of the home anchoring point means. The system alsoincludes packet means for exchanging packets with the home anchoringpoint means via first attachment point means for attaching. The packetsinclude the first IP address.

In other features, the IP address means requests and receives the firstIP address when the mobile terminal is establishing connectivity withthe home network. The system also includes mobility management means forselecting one of host based IP mobility management and network based IPmobility management for the mobile terminal. The IP mobility managementincludes at least one of a Common Management Information Protocol(CMIP), a proxy mobile IP (PMIP) and General Packet Radio ServiceTunneling Protocol (GTP).

In other features, the packet means exchanges packets with the homeanchoring point means via second attachment point means for attachingwhen the mobile terminal is roaming within a range of the secondattachment point means. The mobility management means selects the hostbased IP mobility for communicating with the home anchoring point meansvia the second attachment point means. The first IP address correspondsto a public IP address for the home anchoring point means. One of thepackets further includes a second IP address that includes an IP sourceaddress for payload data of the one of the packets.

In other features, the IP source address indicates a location within apacket data network from which the payload data originated. The systemalso includes access means for requesting connection to the firstattachment point means. The packet means encapsulates outgoing ones ofthe packets with the first IP address, payload data, and a second IPaddress that identifies a destination within a packet data network forthe payload data. The packet means encapsulates outgoing ones of thepackets with a source IP address for the mobile terminal. The mobileterminal selects one of a plurality of types of mobility management.

In other features, the system includes the home anchoring point means.The home anchoring point means selectively provides the first IP addressbased on the selected one of the plurality of types of mobilitymanagement. The system also includes a visited network. The mobileterminal requests the connection to the first attachment point meanswhen roaming in the visited network. The mobile terminal requests theconnection to the first attachment point means when roaming in the homenetwork.

In other features, home anchoring point means for anchoring is locatedwithin a home network. The home anchoring point means includes publicaddress means for selectively providing a public address for the homeanchoring point means in response to selection of the home anchoringpoint means by a device of the home network. The selection is based on aprivate address for the home anchoring point means. The public addressis requested by and is directly addressable by a mobile terminal. Thesystem also includes packet means for exchanging packets with the mobileterminal. The packets include the public address. At least one of thepublic and private addresses includes an Internet protocol (IP) address.

In other features, the system includes mobility management means fordetermining whether the home anchoring point means supports a requestfor mobility from the mobile terminal. The request for mobility includesa request to use one of a Common Management Information Protocol (CMIP),a proxy mobile IP (PMIP) and General Packet Radio Service TunnelingProtocol (GTP). One of the packets further includes a second addressthat includes an IP source address for payload data of the one of thepackets. The IP source address indicates a location within a packet datanetwork from which the payload data originated.

In other features, the packet means encapsulates outgoing ones of thepackets with the first address, payload data, and a second address thatidentifies a source within a packet data network for the payload data.The packet means encapsulates outgoing ones of the packets with a thirdaddress that corresponds to the mobile terminal.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description, the claims and the drawings. Itshould be understood that the detailed description and specific examplesare intended for purposes of illustration only and are not intended tolimit the scope of the disclosure.

BRIEF DESCRIPTION OF DRAWINGS

The present disclosure will become more fully understood from thedetailed description and the accompanying drawings, wherein:

FIGS. 1-3 are functional block diagram of wireless network systemsaccording to the prior art;

FIG. 4 is a functional block diagram of an implementation of proxymobility according to the prior art;

FIG. 5 is a timeline of steps performed when a wireless terminalconnects to a visited network according to the prior art;

FIGS. 6-7 are graphical depictions of a packet being sent by and sent toa wireless terminal, respectively, according to the prior art;

FIG. 8 is a functional block diagram of a network system according tothe present disclosure;

FIG. 9A is a functional block diagram of an exemplary implementation ofterminal mobility for a single attachment point according to the presentdisclosure;

FIG. 9B is an exemplary timeline of network system operations accordingto the present disclosure;

FIG. 10A is a functional block diagram of an exemplary implementation ofhierarchical proxy mobility for a single attachment point according tothe present disclosure;

FIG. 10B is an exemplary timeline of network system operations accordingto the present disclosure;

FIGS. 11A-12 are exemplary graphical depictions of transmission of apacket within a network system according to the present disclosure;

FIGS. 13A-13D are functional block diagrams of network devices accordingto the present disclosure;

FIG. 14 is a flowchart depicting exemplary steps performed for a methodfor allocating an anchoring point according to the present disclosure;

FIG. 15 is a flowchart depicting exemplary steps performed by anattachment point according to the present disclosure; and

FIG. 16 is a flowchart depicting exemplary steps performed by anintermediate anchoring point according to the present disclosure.

DESCRIPTION

The following description is merely exemplary in nature and is in no wayintended to limit the disclosure, its application, or uses. For purposesof clarity, the same reference numbers will be used in the drawings toidentify similar elements. As used herein, the phrase at least one of A,B, and C should be construed to mean a logical (A or B or C), using anon-exclusive logical or. It should be understood that steps within amethod may be executed in different order without altering theprinciples of the present disclosure.

As used herein, the term module refers to an Application SpecificIntegrated Circuit (ASIC), an electronic circuit, a processor (shared,dedicated, or group) and memory that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablecomponents that provide the described functionality. The followingsystems and devices may include 3^(rd) Generation Partnership Project(3GPP) system components and comply with 3GPP technical specifications,some of which are stated herein.

According to the present disclosure, a mobile terminal requests anaddress from an anchoring point that is within a home network. Theanchoring point provides the mobile terminal with a public InternetProtocol (IP) address for the anchoring point. A public address is anaddress that may be directly addressed by a mobile terminal and that maycorrespond to a specific anchoring point. The mobile terminal maytherefore use the public IP address to directly address the anchoringpoint when roaming between access points of the visited network oraccess points in other visited networks.

Previously, anchoring points did not provide public addresses to mobileterminals and instead used private address to communicate with variousnetwork devices other than terminals. The private addresses wereinvisible to terminals. Terminals therefore were not aware of theaddress of the ultimate home anchoring point and instead communicatedwith the various network devices in order to communicate through theultimate home anchoring point.

Referring now to FIG. 8, a functional block diagram depicts an exemplaryimplementation of a network system 300 that includes a hierarchicalproxy mobility architecture, according to the present disclosure.Alternative embodiments do not require the proxy mobile structure andmay merely include communications between the mobile terminal 314 anddevices within the home network 302. The home network 302 includes ahome anchoring point 306. An example of a home network 302 includes ahome public land mobile network (HPLMN) of a 3GPP network system. Anexample of an anchoring point is a gateway, such as a packet datanetwork (PDN) gateway.

The home anchoring point 306 may communicate with one or more homenetwork servers 309 and a PDN 308 that may include a distributedcommunications system, such as the Internet. The home anchoring point306 allows data transfer between the home network 302 and variousexternal IP services of one or more PDNs, such as the PDN 308. Examplesof home network servers 309 include anauthentication/authorization/accounting (AAA) server 310, a homesubscriber server (HSS) 311 and a home policy and changing rulesfunction (hPCRF) device 313.

A terminal 314, which may include a mobile device such as a mobilephone, connects to the home network 302 via a visited network 318 whenroaming. An example of a visited network includes a visited public landmobile network (VPLMN) of a 3GPP network system. The visited network 318includes one or more attachment points 320. For example, five attachmentpoints 320-1, 320-2, 320-3, 320-4, and 320-5 are shown. The attachmentpoints 320 may include any suitable wireless or wired interface that maycomply with IEEE standards 802.11, 802.11a, 802.11b, 802.11g, 802.11h,802.11n, 802.16, and 802.20, which are incorporated herein in theirentirety.

For example, the attachment point 320-1 may include a 3GPP interface.The attachment point 320-1 may use the Universal MobileTelecommunications System (UMTS) and/or a Long Term Evolution (LTE)Radio Access Network (RAN).

For example, the attachment point 320-2 may include a Worldwideinteroperability for Microwave Access (WiMAX) interface. For example,the attachment point 320-3 may include a wired interface, such as acable modem or a Digital Subscriber Line (DSL). For example, theattachment point 320-4 may include a 3^(rd) Generation PartnershipProject 2 (3GPP2) interface, which may use Code Division Multiple Access2000 (CDMA2000). For example, the attachment point 320-5 may include aWireless Local Area Network (WLAN) interface.

The attachment points 320 may communicate with other networks, such asthe home network 302, via an intermediate anchoring point 330. Theintermediate anchoring point 330 may be, for example, a serving gateway.The visited network 318 may also include a visited policy and changingrules function (vPCRF) device 331. The vPCRF device 331 and the hPCRFdevice 313 may terminate reference points between network devices, suchas reference points associated with each other, the intermediateanchoring point 330, the home anchoring point 306, devices within thePDN 308, etc.

The intermediate anchoring point 330 may also include switching androuting functionality to allow the attachment points 320 to communicatebetween each other. The intermediate anchoring point 330 may communicatewith a mobility management entity (MME) 333, a servicing general packetradio service support node (SGSN) 335, a Radio Access Network (RAN), andthe vPCRF device 331. The SGSN 335 may perform MME selection and/orintermediate anchoring point selection. The visited network 318 mayinclude an AAA proxy 340, which connects to the AAA server 310 of thehome network 302.

For example, the mobile terminal 314 is shown connected to theattachment point 320-1. When the mobile terminal 314 initiates theconnection with the attachment point 320-1, the attachment point 320-1determines whether the mobile terminal 314 is authorized by querying theAAA proxy 340. The AAA proxy 340 may identify the AAA server 310 basedon identification information from the mobile terminal 314, and requestauthorization information from the AAA server 310.

The AAA proxy 340 may cache this data, such as for a specified period oftime or for as long as the mobile terminal 314 is connected to one ofthe attachment points 320 of the visited network 318. In addition, theAAA server 310 may provide an expiration time for this authorizationinformation. The authorization information may include whether themobile terminal 314 is authorized to connect to the visited network 318,what services the mobile terminal 314 should be offered, and whatquality of service the mobile terminal 314 should be guaranteed.

In various implementations, the AAA proxy 340 may provide the address ofthe AAA server 310 to the attachment point 320-1, which then queries theAAA server 310 directly. Access and authorization may be provided by anysuitable method, including via the HSS 311.

Assuming that the mobile terminal 314 is authorized to attach, a firsttunnel is created between the attachment point 320-1 and theintermediate anchoring point 330. A second tunnel is created between theintermediate anchoring point 330 and the home anchoring point 306. Ifthe mobile terminal 314 switches from the attachment point 320-1 toanother of the attachment points 320, or to another 3GPP attachmentpoint (not shown), only the first tunnel may be modified. The secondtunnel, from the intermediate anchoring point 330 to the home anchoringpoint 306, may remain unchanged.

Referring now to FIG. 9A, the mobile terminal 314 initially connects toan attachment point 320, which may be an attachment point in the home orvisited networks 302, 318 or in another network that is not a 3GPP basednetwork. At this time, the mobile terminal 314 may also request a publicaddress in order to communicate directly with an anchoring point, suchas anchoring point 306 that includes a home agent (HA) 414. The publicaddress may be directly addressed by the mobile terminal 314 and maycorrespond to a specific home anchoring point. The attachment point 320receives identification information from the mobile terminal 314. Theidentification information is sent to the AAA server 310, which returnsauthentication information to the attachment point 320.

Alternatively, the mobile terminal 314 may also provide a public IPaddress for a home anchoring point, such as home anchoring point 306,that was previously acquired. The attachment point 320 may recognizethat the address corresponds to an anchoring point, such as the homeanchoring point 306, and may route communications directly to the homeanchoring point 306 without requiring authorization, authentication,etc.

Otherwise, assuming that the mobile terminal 314 is authorized foraccess, the anchoring point 306 may allocate an IP address, IP₁, to themobile terminal 314. The anchoring point 306 may also allocate a publicIP address (IP_(HA)) that designates the home anchoring point 306 inresponse to the request for the public address from the mobile terminal314.

The mobile terminal 314 may use IP_(HA) to connect with the homeanchoring point 306 without requiring authorization, authentication,etc. The address IP₁ from the second HA 414 may also be assigned to themobile terminal 314. In other words, a request from the mobile terminal314 is carried through the network(s) to the HA 414 using mechanisms forestablishing the connectivity between the attachment point 320 and theHA 414. Likewise, the reply from the HA 414 is also carried through thenetwork(s) using the mechanisms for establishing the connectivitybetween the attachment point 320 and the HA 414.

Referring now to FIG. 9B, an exemplary timeline of steps performed whenthe wireless terminal 314 connects to a network is presented. First, thewireless terminal 314 performs access and authentication with theattachment point 320. This may include communicating with an AAA server.Upon authentication, the wireless terminal 314 attempts to attach to theattachment point 320. The mobile terminal 314 may request a publicaddress from an anchoring point in the home network during access andauthentication.

The mobile terminal 314 may also provide selection data duringauthentication and/or attachment that indicates that the mobile terminal314 prefers a HA that is capable of terminal based mobility. In otherwords, the mobile terminal 314 may provide an indication of the type ofIP mobility management desired for handover between accesses when themobile terminal is roaming. Examples of mobility management protocolsinclude Common Management Information Protocol (CMIP), proxy mobile IP(PMIP) and General Packet Radio Service Tunneling Protocol (GTP).

For example, the mobile terminal 314 may include a profile thatindicates that the mobile terminal 314 is capable of mobility. Themobile terminal 314 may generate the selection data based on theprofile. Alternatively, the mobile terminal 314 may track historicaldata of terminal mobility and generate the selection data based on thehistorical data. The historical data may be tracked based on apredetermined time period or based on the life of the mobile terminal314.

Alternatively, the mobile terminal 314 may include a selection device,such as a button, switch, button sequence or other input device, thatallows selection of mobility for the mobile terminal 314. The selectiondata may be based on selection device inputs.

The AAA server may use an identifier of the wireless terminal 314, suchas a network address identifier, that uniquely identifies the wirelessterminal 314. The attachment request requests the public IP address fromthe attachment point 320. The attachment point 320 may determine theappropriate HA, such as HA 414, for the wireless terminal 314.

HA 414 may receive the selection data from the mobile terminal 314 andmay determine whether the requested IP mobility management, such as GTP,is supported. If supported, HA 414 selects the public HA address(IP_(HA)) that may be made “visible” to the mobile terminal 314, andthus the mobile terminal 314 may directly address HA 414 based onIP_(HA). Previously, terminals were not provided with public HAaddresses and therefore did not directly address HAs when roaming.Instead, the terminals would initiate attachment steps for new access ina new network. HA 414 may also allocate an address, IP₁, to the mobileterminal 314. HA 414 may store IP₁ in a mapping of allocated IPaddresses. HA 414 may send a binding acknowledgement that includes IP₁and/or IP_(HA), to attachment point 320. A tunnel is then set up betweenthe attachment point 320 and the HA 414 for transmission of packets toand from the wireless terminal 314.

The attachment point 320 may then assign the address IP₁ to the mobileterminal 314 and also provide the mobile terminal 314 with IP_(HA). Inother words, HA 414 returns the public address, IP_(HA), to the mobileterminal 314 as part of a network-based mobility management procedure.

The first network access of the mobile terminal 314 may provide IP_(HA),to the mobile terminal 314, thereby anchoring mobility and IPconnectivity between the mobile terminal 314 and HA 414. The mobileterminal 314 and HA 414 may setup security features so that the mobileterminal 314 may communicate securely with HA 414 without requiring, forexample, standard AAA communications. The security features may bearranged though the AAA server 310. Alternatively, HA 414 may beassociated with a network security module (not shown) that implementsthe security features based on requests from HA 414.

The mobile terminal 314 may use IP_(HA) to designate HA 414 forhost-based mobility when initiating a second access to a network. Forexample, the mobile terminal 314 may roam to a second visited networkand may therefore lose attachment to the first visited network 318. Themobile terminal 314 may then attach to another attachment point 415 in asecond network. Alternatively, the mobile terminal 314 may not loseconnection to HA 414, but instead the attachment point 320 may handoffcommunications to the attachment point 415. Following attachment, themobile terminal 314 may register with HA 414 using IP_(HA). The mobileterminal 314 therefore may avoid discovery of a home network HA throughthe second visited network, as was previously required, because it candesignate a specific HA.

Referring now to FIG. 10A, in an alternative embodiment, the mobileterminal 314 initially connects to a proxy mobility agent (PMA) 402 ofthe attachment point 320-1. In various implementations, the PMA 402 maybe a part of a user plane entity (UPE), an access service network (ASN)gateway, and/or an electronic packet data gateway (ePDG). The PMA 402receives identification information from the mobile terminal 314.

This identification information may include, for example, a NetworkAddress Identifier (NAI) and/or an International Mobile SubscriberIdentity (IMSI). The identification information is sent to the AAA proxy340. Based on the identification information, the AAA proxy identifiesthe appropriate AAA server. In this case, the AAA server 310 isselected. The AAA proxy 340 sends the identification information to theAAA server 310, which returns authentication information to the PMA 402.

The mobile terminal 314 may also provide a public IP address for theultimate home anchoring point, such as home anchoring point 306. Thepublic address may be directly addressed by the mobile terminal 314 andmay correspond to a specific home anchoring point. The attachment point320-1 may recognize that the address corresponds to an anchoring point,such as the home anchoring point 306, and may route communicationsdirectly to the home anchoring point 306 without requiringauthorization, authentication, etc.

Otherwise, assuming that the mobile terminal 314 is authorized foraccess, the PMA 402 sends a binding update to a HA 406 of theintermediate anchoring point 330. The PMA 402 also transmits informationindicating that the HA 406 is not the ultimate HA of the mobile terminal314. For example, the binding update may include information designatingthe ultimate HA of the mobile terminal 314, which is not the HA 406. ThePMA 402 may be pre-programmed with the location of the HA 406.

In various implementations, the mobile terminal 314 and/or the AAAserver 310 may provide information identifying the ultimate HA, such asthe HA 414 of the home anchoring point 306. The PMA 402 and/or the HA406 may also resolve the ultimate HA identification into an address,such as an IP address. In various implementations, the address of theultimate HA may be resolved from a logical name using a Domain NameSystem (DNS) query. However, the mobile terminal 314 may provide thepublic IP address of the ultimate HA, thus removing need to resolve theaddress of the HA.

The HA 406 allocates an IP address for the mobile terminal 314, whichmay be performed in the same manner as when the HA 406 is the ultimateHA. However, because the HA 406 is not the ultimate HA, the HA 406triggers a second PMA 410 of the intermediate anchoring point 330 tocontact the ultimate HA, which may be HA 414. The second PMA 410 sends abinding update to the second HA 414. The second HA 414 may allocate anIP address, IP₂, to the mobile terminal 314. The second HA 414 may alsoallocate a public IP address (IP_(HA2)) for the home anchoring point306.

The mobile terminal 314 may use IP_(HA2) to connect with the homeanchoring point 306 without requiring authorization, authentication,etc. The address IP₂ from the second HA 414 may also be assigned to themobile terminal 314. Tunnels may then be established between the secondHA 414 and the second PMA 410, and between the HA 406 and the PMA 402.Alternatively, tunnels may be established between the PMA 402 and thesecond HA 414.

Referring now to FIG. 10B, an exemplary timeline of a terminalattachment to a visited network is shown. For ease of explanation, thefirst PMA 402 will be referred to herein as PMA1 402, the second PMA asPMA2 410, the first HA 406 as HA1, and the second HA 414 as HA2. In analternative embodiment, HA2 and PMA2 may correspond to the same entity.The mobile terminal 314 begins access authentication with PMA1 402.Assuming that authentication is successful, the mobile terminal 314attempts to attach to PMA1 402. The mobile terminal 314 may provideselection data during authentication and/or attachment that indicatesthat the mobile terminal 314 prefers a HA that is capable of terminalbased mobility. In other words, the mobile terminal 314 may provide anindication of the type of IP mobility management desired for handoverbetween accesses when the mobile terminal 314 is roaming. Examples ofmobility management protocols include CMIP, PMIP and GTP.

For example, the mobile terminal 314 may include a profile thatindicates that the mobile terminal 314 is capable of mobility. Themobile terminal 314 may generate the selection data based on theprofile. Alternatively, the mobile terminal 314 may track historicaldata of terminal mobility and generate the selection data based on thehistorical data. The historical data may be tracked based on apredetermined time period or based on the life of the mobile terminal314.

Alternatively, the mobile terminal 314 may include a selection device,such as a button, switch, button sequence or other input device, thatallows selection of mobility for the mobile terminal 314. The selectiondata may be based on selection device inputs. PMA1 402 may determine theultimate home anchoring point of the mobile terminal 314 based on theselection data from the mobile terminal 314.

For example, PMA1 402 may select the ultimate home anchoring point basedon the indication of the IP mobility management. Selection may be basedon the ability of the ultimate home anchoring point to support therequest for CMIP. PMA1 402 may select a private HA IP address from aplurality of HA addresses that corresponds to a home anchoring point,such as home anchoring point 306. The private IP address may be visibleonly to network entities and not to the mobile terminal 314. If noselection data is provided from the mobile terminal 314, PMA1 402 maydetermine the ultimate home anchoring point based on other criteria,such as home anchoring point availability. In various implementations,ultimate home anchoring point selection may occur during authentication.

PMA1 402 may send a binding update to HA1 406, which may include anidentifier of the mobile terminal 314 and an identifier of the ultimateHA. These may be referred to as the network address identifier (NAI) andthe HA identifier (HID), respectively. HA1 406 may allocate address IP₁to the mobile terminal 314. Because HA1 406 has received the HID, HA1406 instructs PMA2 410 to bind to the ultimate HA. PMA2 410 locates theultimate HA based on the HID and/or the public address provided by themobile terminal 314.

In various implementations, the binding update from PMA1 402 to HA1 406may omit the HID. Therefore, HA1 406 may automatically determine whatthe ultimate HA of the mobile terminal 314 is. HA1 496 may use the NAIof the mobile terminal 314, a portion of the NAI, and/or the public HAaddress (for example, IP_(HA2)) provided by the mobile terminal 314 tolook up the ultimate HA, such as with an AAA query. HA1 406 may thenknow whether it is the ultimate HA of the mobile terminal 314.Alternatively, the binding update may include an indication that HA1 406is not the ultimate HA. This may prompt HA1 406 to determine theultimate HA of the mobile terminal 314.

When HA1 406 determines that it is not the ultimate HA, it may triggerPMA2 410 to bind to the ultimate HA. HA1 406 may provide the address ofthe ultimate HA, or PMA2 410 may determine this information. Forexample, PMA2 may contact an AAA server and/or a DNS server using theHID. PMA2 410 may also merely bind to an ultimate HA based on the pubicHA address provided by the mobile terminal 314. PMA2 410 may send abinding update, which includes the NAI and/or the public HA address, toHA2 414. HA2 414 may allocate an address, IP₂, to the mobile terminal314. HA2 414 may store IP₂ in a mapping of NAIs and allocated IPaddresses. HA2 414 may receive the selection data from the mobileterminal 314 and may determine whether the requested IP mobilitymanagement, such as CMIP, is supported.

If supported, HA2 414 selects the public HA address (IP_(HA2)) that maybe made “visible” to the mobile terminal 314, and thus the mobileterminal 314 may directly address HA2 414 based on IP_(HA2). HA2 414 maysend a binding acknowledgement that includes IP₂ and/or IP_(HA2), toPMA2 410. PMA2 410 and HA2 414 may then set up a common tunnel. PMA2 410may forward IP₂ and IP_(HA2) to HA1 406. HA1 406 may then send a bindingacknowledgment including IP₂ and/or IP_(HA2) to PMA1 402. PMA1 402 andHA1 406 may set-up a common tunnel. PMA1 402 may then assign the addressIP₂ to the mobile terminal 314 and provide the mobile terminal 314 withIP_(HA2). In other words, HA2 414 returns the public address, IP_(HA2),to the mobile terminal 314 as part of a network-based mobilitymanagement procedure.

The first network access of the mobile terminal 314 may provideIP_(HA2), to the mobile terminal 314, thereby anchoring mobility and IPconnectivity between the mobile terminal 314 and HA2 414. The mobileterminal 314 and HA2 414 may setup security features so that the mobileterminal 314 may communicate securely with HA2 414 without requiring,for example, AAA proxy communications. The security features may bearranged though the AAA server 310. Alternatively, HA2 may be associatedwith a network security module (not shown) that implements the securityfeatures based on requests from HA2 414.

The mobile terminal 314 may use IP_(HA2) to designate HA2 414 forhost-based mobility when initiating a second access to a network. Forexample, the mobile terminal 314 may roam to a second visited networkand may therefore lose attachment to the first visited network 318. Themobile terminal 314 may then attach to a PMA (PMA1′ 500) in the secondnetwork. Alternatively, the mobile terminal 314 may not lose connectionto HA2 414, but instead PMA1 402 may handoff communications to PMA1′500. Following attachment, the mobile terminal 314 may register with HA2414 using IP_(HA2). The mobile terminal 314 therefore may avoiddiscovery of a home network HA through the second visited network, aswas previously required.

Referring now to FIG. 11A, a packet 502 is shown being transmitted bythe mobile terminal 314. The packet 502 includes a source address ofIP₂, which has been assigned to the mobile terminal 314. The destinationaddress, which is routable from HA2, is denoted IP_(dest). The packet502 may also include an HA address, IP_(HA2), that designates HA2 as ananchor point. The packet 502 may also include a payload. The packet 502may initially be sent to PMA1 402. PMA1 402 encapsulates the packet 502into a payload of a first encapsulating packet 504.

The first encapsulating packet 504 has a source address of PMA1 402,IP_(PMA1), and a destination address of the intermediate anchoring point330, IP_(IAP). HA1 extracts the packet 502 from the first encapsulatingpacket 504. Based on the source address of the packet 502 and/or the HA2address for the packet, PMA2 410 recognizes that the packet 502 shouldbe passed to HA2 414.

PMA2 410 encapsulates the packet 502 into a second encapsulating packet506. The second encapsulating packet 506 has a source address ofIP_(IAP) and a destination address of HA2 414, IP_(HA2). Alternatively,a different address may be used to address HA2 414 from PMA2 410, whichmay be referred to as HA2′, which may represent a private address forHA2 414. The private address may be used between network devices evenwhen the public address IP_(HA2) is used to designate HA2 414. However,network devices may recognize both public and private addresses from HA2414 and may interchange the addresses. The mobile terminal 314, however,may only use and recognize IP_(HA2). HA2 414 extracts the packet 502from the second encapsulating packet 506 and forwards the packet 502 tothe noted destination address, IP_(dest). For example, IP_(dest) may bewithin the PDN 308, within the home network, or within a visitednetwork.

Referring now to FIG. 11B, a packet 512 being transmitted to the mobileterminal 314 is shown. The packet 512 may have a destination address ofIP₂, which has been assigned to the mobile terminal 314. The packet 512may also have a source address designated IP_(src)) and may include apayload. The packet 512 may also include a public address for HA2 414,IP_(HA2). When HA2 414 receives packets with a destination address ofIP₂, they are tunneled to the mobile terminal 314.

The packet 512 is therefore encapsulated in a payload of a firstencapsulating packet 514. The first encapsulating packet 514 has asource address of IP_(HA2) and a destination address of IP_(IAP). PMA2extracts the packet 512 from the first encapsulating packet 514. BecauseIP₂, the destination address of the packet 512, is associated with PMA1,PMA2 forwards the packet 512 to HA1 for tunneling to PMA1.

HA1 encapsulates the packet 512 into a payload of a second encapsulatingpacket 516. The second encapsulating packet 516 has a source address ofIP_(IAP) and a destination address of IP_(PMA1). PMA1 receives thesecond encapsulating packet 516 and extracts the packet 512. The packet512 is then forwarded to the destination address, IP₂, which has beenassigned to the mobile terminal 314. The mobile terminal 314 may alsoextract the IP_(HA2) from the packet for communications with the PDN308. For example, packets may include a predetermined order for data,such as Src, Dest, HA2, and payload. When an IP address is in one of thepositions, for example, the HA2 position, the mobile terminal 314 maydetermine that IP_(HA2) corresponds to a public address of a homeanchoring point. In FIGS. 11A-11B, PMA1 402 and the intermediateanchoring point 330 are used. However, alternative embodiments do notinclude intermediate anchoring point and merely include the mobileterminal 314 communicating with a HA via an attachment point.

Referring now to FIG. 12, the mobile terminal 314 may roam to adifferent network or out of range of PMA1 402 and may attach to adifferent proxy mobility agent (for example, PMA1′ 500). When the mobileterminal 314 has been provided with a public address for a homeanchoring point, IP_(HA2), the mobile terminal 314 may transmit a packet517 that includes IP_(HA2). The packet 517 may therefore be routedthrough HA2 instead of a different home anchoring point. The packet 517may also include source and destination addresses (IP_(src), IP_(dest),respectively) and a payload.

Further, when the packet 517 includes a home anchoring point address,such as IP_(HA2), PMA1′ 500 may determine that the mobile terminal 314does not require authorization and/or other steps required for initialattachments to a network. PMA1′ 500 may encapsulate the packet 517 in anencapsulating packet 518 that includes a source address for PMA1′(IP_(PMA1′)) and IP_(HA2), which corresponds to the home anchoring pointdestination for the packet 517. PMA 1′ 500 may also determine theultimate destination of the packet 517 based on the destination address,IP_(dest). HA2 extracts the packet 517 from the encapsulating packet518, and forwards the packet 517 to the noted destination address,IP_(dest). For example, IP_(dest) may be within the PDN 308, within thehome network, or within a visited network.

Referring now to FIGS. 13A-13D, functional block diagrams of exemplarynetwork devices of the network system 300 are shown. The attachmentpoint 320 may include a RAN, a WLAN, a WiMAX network, a cellularnetwork, etc. The home network server(s) 309 may include a HSS, an AAAserver, a remote server, etc. The mobile terminal 314 may provide theattachment point 320 with service request information, IP connectivityprotocol information, PDN information, and/or HA information. The mobileterminal 314 may communicate with the home network server(s) 309 via theattachment point 320 and/or an intermediate anchoring point 330 to setupconnectivity and mobility tunnel(s). The mobile terminal 314 may use theconnectivity and mobility tunnel(s) for communication between the mobileterminal 314 and the home anchoring point 306. The tunnel(s) may includea connectivity tunnel and/or a mobility tunnel.

The mobile terminal 314 may include an antenna 520, an analog front-endmodule 522, a transmit module 524, a receive module 526, and a controlmodule 528. The analog front-end module 522 may transmit signalsgenerated by the transmit module 524 via the antenna 520 and may outputsignals received from the antenna 520 to the receive module 526. Themobile terminal 314 may also include an IP connectivity generator 530for the generation of IP descriptors and/or IP connectivity indicators.An IP connectivity generator may be included in one of the other networkdevices, such as in the attachment point 320, the intermediate anchoringpoint 330, the home anchoring point 306, etc.

In FIG. 13B, the control module 528 may include an access module 531that initiates access with an attachment point of an external network,such as the visited network 318. If the mobile terminal 314 roamsoutside of the range of the attachment point and/or the visited network,the access module 531 may initiate access communications with a newattachment point and/or network. The control module 528 may also includea packet module 532 that constructs, sends and receives packets.

The packet module 532 may also determine the contents of a packet, suchas the packet 512 of FIG. 11B. A home IP address module 533 maydetermine whether the packet 512 includes an IP address for the homeanchoring point and may store the IP address in memory 534. The packetmodule 532 and the access module 531 may use the identified IP addressin subsequent communications. The control module 528 may also include amobility management module 535. The mobile terminal 314 may selectbetween host based and network based mobility, including CMIP, PMIP,and/or GTP when roaming.

The attachment point 320 may include an antenna 540, an analog front-endmodule 542, a transmit module 544, a receive module 546, and a controlmodule 548. The control module 548 may correspond to a proxy mobileagent 402. The analog front-end module 542 may transmit signalsgenerated by the transmit module 544 via the antenna 540 and may outputsignals received from the antenna 540 to the receive module 546.

In FIG. 13C, the control module 548 may include a communication module550 that receives and analyzes access requests from mobile terminals andpackets from mobile terminals and external networks. The access requestsand/or the packets may include a public IP address for a home anchoringpoint. An IP address module 552 may determine that the terminal sent apacket and/or an access request that includes the public IP address ofthe home anchoring point and may route communications via a routingmodule 554 from the terminal directly to the home anchoring point basedon the public IP address. The IP address module 552 may determine thatthe IP address corresponds to an IP address of a home anchoring point bycomparing the IP address to IP addresses for various anchoring pointsstored in memory 556.

The home network server(s) 309 may include an antenna 560, an analogfront-end module 562, a transmit module 564, a receive module 566, and acontrol module 568. The analog front-end module 562 may transmit signalsgenerated by the transmit module 564 via the antenna 560 and may outputsignals received from the antenna 560 to the receive module 566. Thehome network server(s) 309 may include PDN records 570 and mobileterminal records 572 stored within memory 573.

The intermediate anchoring point 330 may include an antenna 580, ananalog front-end module 582, a transmit module 584, a receive module586, and a control module 588. The control module 588 may correspond toa home agent 406 and/or a proxy mobile agent 410. The analog front-endmodule 582 may transmit signals generated by the transmit module 584 viathe antenna 580 and may output signals received from the antenna 580 tothe receive module 586.

The home anchoring point 306 may include an antenna 590, an analogfront-end module 592, a transmit module 594, a receive module 596, and acontrol module 597. The control module 597 may correspond to a proxyhome agent 414. The analog front-end module 592 may transmit signalsgenerated by the transmit module 594 via the antenna 590 and may outputsignals received from the antenna 590 to the receive module 596. Thehome anchoring point 306 may be in communication with a PDN 308 thatprovides operator IP services 599.

In FIG. 13D, the control module 597 may include a packet module 600 thattransmits and receives packets with external network devises via thetransmit/receive modules 594, 596. The control module 597 may include apublic home IP address module 602 that provides a public IP address (forexample IP_(HA)) that is included with the packets that are transmittedexternally. The control module 597 may also include a source analysismodule 604 that determines that a particular mobile terminal sent apacket. The public home IP address module 602 may provide a differentpublic IP address for different terminals based on source analysismodule signals. The control module 597 may store profiles for terminalsin memory 609 and/or may receive profile data for terminals from amemory within a home network server 309.

The control module 597 may also include a private address module 610that recognizes requests to use the home anchoring point 306 fromdevices in the network system 300, such as the intermediate anchor point330. The requests may include a private address for the home anchoringpoint 306. The private address may be visible to network devices, suchas the home network server 309 and the intermediate anchoring point 330but may be invisible to mobile terminals. In other words, mobileterminals may not directly address the home anchoring point 306 using aprivate address for the home anchoring point 306. An IP inabilitymanagement module 610 may receive communications from network devicesthat are addressed using the private address.

The communications may include requests to connect from the mobileterminal 314 and my also include an indication of a mobility managementselection or preference from the mobile terminal 314. The IP mobilitymanagement module 610 may determine whether the selected mobility (forexample, host or network mobility) is supported by the home anchoringpoint 306. If it is, the home anchoring point 306 may provide the publicIP address to the mobile terminal 314. Otherwise, devices in the network300 may select a different home anchoring point and/or the homeanchoring point 306 may refuse to accept communications with the mobileterminal 314.

The embodiments disclosed herein enable a mobility mode. The mobilitymode refers to the ability of a mobile terminal to roam between localand/or global networks. The mobility mode is setup based on mobileterminal and network system mobility capabilities, mobility preferences,and mobile terminal profiles and may refer to selected inabilityprotocols for IP connectivity and handoff, as well as a selected homeanchoring point 306. The decision to operate in a mobility mode may bemade by a home network, and may change based on updated mobile terminalparameters and/or network system parameters.

When the connectivity protocol is host-based, the control module may setup the connectivity tunnel between the mobile terminal 314 and theattachment point 320 of a remote network using a host-based protocol(for example, CMIP). For example, the attachment point 320 mayrespectively function as an access router when the CMIP is MIPv4 orMIPv6, which are incorporated herein in their entirety.

When the connectivity protocol is network-based, the attachment point320 may set up the connectivity tunnel between the mobile terminal 314and the attachment point 320 and/or between the attachment point 320 andan intermediate anchoring point 330 using a network-based protocol (forexample, PMIP).

The mobile terminal 314 may communicate with a remote network via themobility tunnel when the mobile terminal 314 roams from, for example,one local network to another (for example, from a WLAN to a cellularnetwork). The intermediate anchoring point 330 may handoff a mobilitytunnel from one local network to another when the mobile terminal 314roams between local networks. Referring now to FIG. 14 a flowchartdepicts exemplary steps performed by the mobile terminal. Control beginsin step 650 when a mobile terminal 314 attempts to gain accessconnectivity with the network 302 at the access level. For example, themobile terminal 314 may perform an Evolved Universal Terrestrial RadioAccess Network (eUTRAN) network attachment. Alternatively, the mobileterminal 314 may trigger a network parameter configuration usingNeighbor Discovery mechanisms or a Dynamic Host Configuration Protocol(DHCP).

In step 652, the mobile terminal 314 may provide an indication of thetype of IP mobility management desired, for example, CMIP, PMIP, or GTP,for handover between accesses. The mobile terminal 314 may also requesta public address that corresponds to a home anchoring point within thehome network. In step 654, a home anchoring point is selected in thehome network 302 for a particular PDN by a network device, for example,an attachment point, such as PMA 410. The PDN and/or home anchoringpoint may be selected based on the indication of the mobility managementfrom the mobile terminal 314 to, for example, support the request forCMIP, PMIP, or GTP. Devices within the network, such as PMA 410, may usea private address to communicate and/or select the selected homeanchoring point based on the request from the mobile terminal 314. Theselected home anchoring point may interact with the HSS/AAA to store theprivate address.

In step 656, if the selected home anchoring point does not support thedesired mobility, a network device, such as PMA 410, for example, mayselect a different home anchoring point in step 658. Otherwise, in step660, the home anchoring point is provided with the request from themobile terminal 314 for a public address for the home anchoring point.The home anchoring point then selects a public address, which is theaddress that can be made visible to the mobile terminal 314 and that canbe addressed directly by the mobile terminal 314. The home anchoringpoint therefore ultimately receives the request for the public addressfrom the mobile terminal 314 and responds by generating or otherwiseselecting a public address.

In step 662, the home anchoring point returns its public address to theaccess network as part of network-based mobility management procedures.The access network, which may be the home or visited network 302, 318provides to the mobile terminal 314 the public address. The mobileterminal 314 thus has a public address of the core network elementanchoring the mobility and the IP connectivity. The mobile terminal 314may then, for example, use the public address as the home agent for thehome anchoring point for host-based mobility when moving to anotheraccess using host-based mobility.

Referring now to FIG. 15, a flowchart depicts exemplary steps performedby the first PMA 402 when the mobile terminal 314 is roaming in avisited network. Control begins in step 802, where control determineswhere an access request has been received. If so, control transfers tostep 803; otherwise, control transfers to step 804. In step 803, controldetermines whether the access request includes a public IP address(IP_(HA2)). If so, control transfers to step 805. If not, controltransfers to step 806; otherwise, control transfers to step 804. In step806, control contacts an AAA server to determine whether the terminal isauthorized to attach. Control continues in step 808.

In step 808, if the AAA process determines that the terminal isauthorized to attach, control continues in step 810; otherwise, controltransfers to step 804. In step 810, control sends a binding update withthe network address identifier of the terminal to the intermediateanchoring point. Control then continues in step 804.

In step 804, control determines whether a binding acknowledgement hasbeen received. If so, control transfers to step 812; otherwise, controlstransfers to step 805. In step 812, control sets up a tunnel to the HA406 from which the binding acknowledgement was received. The HA may belocated in the intermediate anchoring point 330, and may share an IPaddress with the intermediate anchoring point 330. Control thencontinues in step 816, where the address received in the bindingacknowledgement is assigned to the mobile terminal 314. Control thencontinues in step 805.

In step 805, control determines whether a packet has been received froma mobile terminal 314. If so, control transfers to step 818; otherwise,control transfers to step 820. In step 818, control encapsulates thepacket and sends the encapsulated packet to the HA 406 in theintermediate anchoring point 330 if IP_(HA2) is not provided by themobile terminal 314. Alternatively, control sends the packet to the HA414 in the home anchoring point 306 if IP_(HA2) is provided by themobile terminal 314.

Control then continues to step 820. In step 820, control determineswhether a packet has been received from the intermediate anchoring point330. If so, control transfers to step 822; otherwise, control returns tostep 802. In step 822, control decapsulates the packet and sends thepacket to the destination address. The destination address will likelybe that of the terminal. Control then returns to step 802.

Referring now to FIG. 16, a flowchart depicts exemplary steps performedby the intermediate anchoring point 330. Control begins in step 902,where control determines where a binding update has been received. Ifso, control transfers to step 904; otherwise, control transfers to step906. In step 904, control may allocate an IP address, IP₁, to the mobileterminal 314 that triggered the binding update.

Control then continues in step 908, where control determines whether thebinding update includes an NAI. If so, control transfers to step 910; ifnot, control transfers to step 912. An NAI may indicate that theultimate HA is not in the intermediate anchoring point 330. The NAI maybe based on, for example, the presence of a public IP address for a HAin communications from the mobile terminal 314. Therefore, in step 910,control determines the address of the ultimate HA.

For example, control may provide the NAI to an AAA server to determinethe ultimate HA address. Alternatively, control may extract the IPaddress for the ultimate HA from a received packet from the mobileterminal 314. The intermediate anchoring point 330 may serve as a HA inaddition to providing hierarchical proxy mobility between a proxymobility agent and another HA.

The NAI may include a HID, which may include a logical name or networkaddress for the ultimate HA. The HID may be based on the IP_(HA2)provided by the mobile terminal 314 and/or by the ultimate HA 414.Control may resolve a logical name into a network address, such as byusing a DNS query. The HID may already include the network address whenthe PMA sending the binding update has already performed thisresolution.

Control continues in step 914, where a binding update is sent to theultimate HA, which may have been identified by an HID. The bindingupdate may be sent with a source address of the address of theintermediate anchoring point 330, such as shown in FIG. 11A.Alternatively, the binding update may be sent with a source address ofthe allocated address, IP₁, such as is shown in FIG. 12A. Control thencontinues in step 906.

In step 912, the intermediate anchoring point 330 is the ultimate HA,and so a binding acknowledgement is returned to the first PMA 402, PMA1,including the allocated address, IP₁. Control continues in step 906. Instep 906, control determines whether a binding acknowledgement has beenreceived. If so, control transfers to step 916; otherwise, controltransfers to step 918.

In step 916, control stores the received IP address as IP₂. Control maycreate a table entry matching IP₂ with the PMA that originated thebinding process. Control continues in step 920, where control sets up atunnel between PMA2 410 and the sender of the binding acknowledgement,HA2 414. Control continues in step 922, where control sends a bindingacknowledgment including IP₂ to PMA1 402. Controls continue in step 918.

In step 918, control determines whether an encapsulated packet has beenreceived. If so, control transfers to step 924. Otherwise, controlreturns to step 902. In step 924, the packet is decapsulated. Controlcontinues in step 926, where control determines if the destination ofthe packet is a terminal connected within the visited network. If so,control transfers to step 928; otherwise, control transfers to step 930.In step 926, control may check if the packet destination is any of theIP addresses, such as IP₂, assigned to terminals connected to theintermediate anchoring point 330.

In step 928, control encapsulates the packet and sends it to theappropriate PMA. Control then returns to step 902. In step 930, controlencapsulates the packet and sends the packet to the appropriate HA,which is HA2 414 in this example. Control then returns to step 902.

Those skilled in the art can now appreciate from the foregoingdescription that the broad teachings of the disclosure can beimplemented in a variety of forms. Therefore, while this disclosureincludes particular examples, the true scope of the disclosure shouldnot be so limited since other modifications will become apparent upon astudy of the drawings, the specification, and the following claims.

1. A first network configured to connect a terminal to a home networkduring a time that the terminal is roaming within the first network, thefirst network comprising: a plurality of attachment points, wherein afirst attachment point of the plurality of attachment points isconfigured to receive an attach request from the terminal, and whereinthe attach request includes a request from the terminal for an InternetProtocol (IP) address from an anchoring point within the home network;and an Authentication/Authorization/Accounting server proxy configuredto determine whether the terminal is authorized to attach to the firstattachment point, wherein in response to the terminal being authorizedto attach to the first attachment point, i) a first tunnel is createdbetween the first attachment point and a second attachment point of theplurality of attachment points, and ii) a second tunnel is createdbetween the second attachment point and the anchoring point within thehome network; wherein the first attachment point is configured toinitially receive the Internet Protocol (IP) address from the anchoringpoint within the home network via the i) first tunnel and ii) the secondtunnel, and wherein in response to the terminal switching from the firstattachment point to a third attachment point of the plurality ofattachment points, the second tunnel between the second attachment pointand the anchoring point within the home network remains unchanged. 2.The first network of claim 1, wherein the first network comprises avisited network.
 3. The first network of claim 2, wherein the visitednetwork comprises a visited public land mobile network (VPLMN) of a 3GGPnetwork system.
 4. The first network of claim 1, wherein the firstattachment point comprises a 3GPP interface.
 5. The first network ofclaim 1, wherein the Authentication/Authorization/Accounting server isconfigured to determine what services the terminal should be offered inresponse to the first attachment point receiving the attach request. 6.The first network of claim 1, wherein theAuthentication/Authorization/Accounting server is configured todetermine what quality of service should be guaranteed to the terminalin response to the first attachment point receiving the attach request.7. The first network of claim 1, wherein the Internet Protocol (IP)address received from the anchoring point within the home networkcomprises: a public Internet Protocol (IP) address that designates theanchoring point within the home network
 8. The first network of claim 1,wherein: during authentication of the terminal, the terminal isconfigured to provide, to the anchoring point within the home network,an indication of a type of IP mobility management desired for handoverbetween accesses while the terminal is roaming.
 9. The first network ofclaim 8, wherein the type of IP mobility management comprises one ormore of: Common Management Information Protocol (CMIP), proxy mobile IP(PMIP), and General Packet Radio Service Tunneling Protocol (GTP).